Dynamic management and redistribution of contact center media traffic

ABSTRACT

A system that supports multiple contact centers includes a communications network that is coupled between a private network (e.g. MPLS network) and a remote computing environment (e.g. cloud environment). A server system in the remote computing environment monitors health of different network segments (e.g. bandwidth of the connection between the communications network and the remote computing environment, bandwidth of a link used by a tenant to access the private network, etc.). When it is determined that quality of service for voice conversations for one or more contact centers is at risk due to a health status parameter of a network segment reaching a threshold, an appropriate system reaction is triggered. The system reaction may be to offload future calls to a peer remote computing environment to service future calls. The system reaction may also be to cancel outbound campaigns, provide pre-determined “sorry” messages, and the like.

BACKGROUND

Public wide area networks like the Internet are operated by hundreds ofInternet Service Providers, each responsible for a segment of thenetwork. No single entity in this public environment is responsible forhow packets are routed from beginning to end. Thus, packets traversingthe Internet often encounter congestion, significant jitter, and evenloss. For some communications more than others, such as, for example,voice over IP (VoIP) communications or other real time mediacommunications, it is important to provide preferential delivery serviceto avoid the uncertainties of traversing the Internet. However, thepublic Internet generally does not provide end-to-end QoS guaranteesdesired for VoIP communications. It is typical to overcome thelimitations of the public Internet with moving the Voice communicationsto private networks, such as MPLS, where Quality of service (QoS)guarantees help provide such preferential delivery service by ensuringsufficient bandwidth, controlling latency and jitter, and reducing dataloss.

Unexpected call bursts may also affect call quality of existing andfuture calls. With respect to customer contact centers, existingsolutions attempt to manage such unexpected call bursts. Such solutionsmay monitor available contact center resources such as, for example,servers, agents, and media ports. If shortage or failure of a particularresource is detected, a particular action is triggered. For example, theaction may be to keep a calling party on hold if shortage of agents aredetected, switch to a backup server if failure of a current server isdetected, or monitor a number of active calls and alert a systemsadministrator or refuse establishing conversations for new calls once athreshold is reached. Although such solutions may be acceptable tosituations where a single contact center (referred to as a tenant)utilizes system resources and where such resources are predetermined andpre-allocated, it may not be acceptable in situations where multipletenants are supported and resources are shared. In addition, suchexisting solutions do not take into account the quality of establishedvoice conversations in efforts to provide a particular level of qualityfor the established voice conversations. Furthermore, existing solutionsgenerally do not allow a buffer for gracious and gradual degradation ofservice. For example, existing contact center systems may abruptly startrefusing new conversations when a particular threshold is reached, whichmay result in negative end user experience and loss of customers for thecontact center.

Accordingly, what is desired is a system and method for managing voiceand other media traffic associated with contact centers when such systemsupports multiple tenants that share resources.

SUMMARY OF THE INVENTION

According to one embodiment, the present invention is directed to asystem and method for managing media traffic for a plurality of customercontact centers. The system includes first and second server systems inrespectively first and second computing environments, where the firstand second server systems host contact center applications forprocessing communication to and from the one or more contact centers.The system also includes an edge device deployed in a firstcommunications network for facilitating a first communication involvinga first end device and for signaling the first server system to servicethe first communication. Media traffic is transmitted between the firstend device and the first server system during the first communication inresponse to the servicing. The servicing invokes a first contact centerapplication hosted by the first server system. Further, the mediatraffic traverses a first network link coupling the first communicationsnetwork and the first computing environment. The first server system isconfigured to monitor status of the first network link and in responseto the monitoring, signal the second server system in the secondcomputing environment to service a second communication involving asecond end device. The servicing of the second communication invokes asecond contact center application hosted by the second server system.

According to one embodiment of the invention, the first and secondcommunications are voice communications.

According to one embodiment of the invention, the media traffic is voicetraffic.

According to one embodiment of the invention, the first and secondcomputing environments are cloud computing environments.

According to one embodiment of the invention, the monitoring of thestatus of the first network link includes monitoring the bandwidth ofthe first network link.

According to one embodiment of the invention, a second communicationsnetwork is coupled to the first communications network over a secondnetwork link. The second communications network is coupled to the secondcomputing environment. The first server system is further configuredmonitor status of the second network link and select the secondcomputing environment for servicing the second communication based onthe monitored status of the second network link.

According to one embodiment of the invention, the second communicationis configured to generate traffic that traverses the second networklink.

According to one embodiment of the invention, a second communicationsnetwork is coupled to the second computing environment over a secondnetwork link. The first server system is further configured monitorstatus of the second network link and select the second computingenvironment for servicing the second communication based on themonitored status of the second network link.

According to one embodiment of the invention, the first server system isconfigured to select a media type. The first server system is configuredto signal the second server system in the second computing environmentif the second communication is of the selected media type. The selectedmedia type may be a voice treatment in an outbound campaign by one ormore of the plurality of customer contact centers, a voice treatment foran inbound call directed to one or more of the plurality of customercontact centers, or a multi-party call.

According to one embodiment of the invention, the first server system isconfigured to select a contact center service level from a plurality ofavailable service levels, and further configured to signal the secondserver system in the second computing environment if the secondcommunication is associated with a customer contact center assigned tothe selected contact center service level.

According to one embodiment of the invention, the first end deviceaccesses a private network over a second link, where the private networkis coupled to the first communications network. The first server systemis configured to identify one of the plurality of customer contactcenters associated with the first communication, determine availabilityof the second link for the identified customer contact center, and inresponse to the determined availability, trigger an action forpreserving a particular quality of service for the voice communication.

According to one embodiment of the invention, availability of the secondlink includes determining estimated available bandwidth of the secondlink.

According to one embodiment of the invention, the second link isaccessed by an agent of the identified customer contact center via thefirst end device.

According to one embodiment of the invention, the triggered action iscanceling an outbound campaign for the identified customer contactcenter.

According to one embodiment of the invention, the triggered action isactivating a greeting for delivery to the first end user, where thegreeting for indicating inability for servicing the voice communication.

According to one embodiment of the invention, the first end deviceaccesses the first communications network over a second link couplingthe first communications network to a private network. The first serversystem is configured to determine availability of the second link basedon calls traversing the second link. In response to the determinedavailability of the second link, the first server system is configuredto trigger an action with respect to calls associated with contactcenters subscribed to a first service level for preserving a particularquality of service for calls associated with contact centers subscribedto a second service level different from the first service level.

According to one embodiment of the invention, the second link is sharedby customers of the contact centers subscribed to the first and secondservice levels.

According to another embodiment, the present invention is directed to asystem for managing media traffic associated with a plurality ofcustomer contact centers where the system includes an edge devicedeployed in a communications network for facilitating calls betweenagents and customers of the plurality of contact centers. The agents andcustomers access the communications network respectively over agent andcustomer private networks. The agents connect to the agent privatenetwork via a first link, and the customers connect to thecommunications network via a second link traversing the customer privatenetwork. A server system in a computing environment coupled to thecommunications network is configured to identify calls between theagents and the customers; identify one of the plurality of customercontact centers associated with the identified calls; determineavailability of the first link for the identified customer contactcenter; and in response to the determined availability for theidentified customer contact center, triggering an action for preservinga particular quality of service for the identified customer contactcenter.

According to another embodiment, the present invention is directed to asystem for managing media traffic associated with a plurality ofcustomer contact centers where the system includes an edge devicedeployed in a communications network for facilitating calls betweenagents and customers of the plurality of contact centers. The agents andcustomers access the communications network respectively over agent andcustomer private networks. The agents connect to the agent privatenetwork via a first link, and the customers connect to thecommunications network via a second link traversing the customer privatenetwork. A server system in a computing environment coupled to thecommunications network is configured to identify calls between theagents and the customers; determine availability of the second linkbased on the identified calls traversing the second link; and inresponse to the determined availability of the second link, trigger anaction with respect to calls associated with contact centers subscribedto a first service level for preserving a particular quality of servicefor calls associated with contact centers subscribed to a second servicelevel different from the first service level.

A person of skill will recognize that the dynamic management andredistribution of contact center media traffic helps provide well-timedreaction to bandwidth saturation, status change of redundant links, andother “health” related information.

These and other features, aspects and advantages of the presentinvention will be more fully understood when considered with respect tothe following detailed description, appended claims, and accompanyingdrawings. Of course, the actual scope of the invention is defined by theappended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram of a system for dynamic managementand redistribution of contact center media traffic according to oneembodiment of the invention;

FIG. 2 is a schematic block diagram of two geographic regions eachsupporting a system for dynamic management and redistribution of contactcenter media traffic according to one embodiment of the invention;

FIG. 3A is a schematic block diagram depicting details of the dedicatedcommunications network according to one embodiment of the invention;

FIG. 3B is a schematic block diagram depicting details of the dedicatedcommunications network according to another embodiment of the invention;

FIG. 4 is a more detailed schematic block diagram of a server system ina remote computing environment according to one embodiment of theinvention;

FIG. 5 is a schematic diagram depicting a flow of signals betweenvarious components of the system of FIG. 1, for processing an inboundcall from an end user to a contact center according to one embodiment ofthe invention;

FIG. 6 is a flow diagram of an offload process implemented by a trafficmanagement module according to one embodiment of the invention;

FIG. 7 is a semi-schematic, conceptual layout diagram of a portion of atenant's profile record providing information on call resourcesavailable to the tenant according to one embodiment of the invention;

FIG. 8 is a semi-schematic, conceptual layout diagram of another portionof a tenant's profile record for storing information on bandwidthcharacteristics of a tenant MPLS link subscribed to by the tenant forconnecting to a dedicated communications network according to oneembodiment of the invention;

FIG. 9 is a semi-schematic, conceptual layout diagram of a bandwidthconsumption table storing information on a bandwidth of a tenant MPLSlink that is estimated to be consumed for a particular tenant accordingto one embodiment of the invention;

FIG. 10 is a flow diagram of a process executed by a traffic managementmodule for managing traffic bursts on a per tenant basis according toone embodiment of the invention; and

FIG. 11 is a flow diagram of a process for managing unexpected call ratebursts for an entire system according to one embodiment of theinvention.

DETAILED DESCRIPTION

In general teems, embodiments of the present invention are directed to asystem that supports multiple contact centers (referred to as tenants)and manages resources and invokes actions for preserving a particularquality of service for calls (voice and/or real time media traffic)between agents and customers associated with the various contactcenters. The system includes a communications network that is coupledbetween a private network (such as an MPLS network) and a remotecomputing environment (such as a cloud environment). One or more serversin the remote computing environment monitor health status parameters ofdifferent network segments. For example, the servers may monitor networkconnectivity of tenants to the private network, shared networkconnectivity of the tenants to the communications network, sharednetwork connectivity of the customers to the communications network,connectivity between the communications network and the remote computingenvironment in local and peer regions, and/or connectivity between thecommunications network and other communications networks in peerregions. The monitoring may indicate insufficient resources (e.g.bandwidth saturation) or unacceptable quality of the media communicationon a particular network segment.

According to one embodiment, the one or more servers are configured toidentify the connections that are impacted once a call between acustomer and an agent of a contact center is in progress. In the eventof unexpected call bursts affecting one or more contact centers, thesystem is configured to handle the call bursts in a graceful manner withcontrollable service degradation for newly arriving calls with regardsto the level/class of services and call profiles to which the differentcontact centers have subscribed.

According to one embodiment, the system maintains a number of thresholdsper network segment, including capacity and quality related metrics.When it is determined that quality of service for voice conversationsand other real time media communication (collectively referred to asvoice conversations or calls), is at risk due to one or more healthstatus parameters of a network segment reaching a threshold, anappropriate system reaction is triggered. The system reaction may be toinvoke a customized voice treatment, allow the customers to leave avoice mail of a pre-defined duration, redirect the call to an externalvoice mail system, request a call back at a later time, or provideanother pre-determined “sorry” message. The providing on behalf of aparticular tenant the gradual service degradation and customization ofvoice treatments is based on whether the particular tenant hassubscribed to such service. By subscribing to the service, contactcenters can be assured that new calls that cannot be immediatelyserviced will be gracefully turned away if necessary.

FIG. 1 is a schematic block diagram of a system 1 for dynamic managementand redistribution of contact center media traffic according to oneembodiment of the invention. The system includes a communicationsnetwork 10 which, according to one embodiment, is dedicated tofacilitate calls between agents 12 of various contact centers, andcustomers and other end users 14. The calls may include, for example,VoIP communication and any other media (e.g. Real-time TransportProtocol (RTP)) communication conventional in the art. The calls arecontrolled by any signaling protocol configured to control communicationsessions over the Internet, such as, for example, session initiationprotocol (SIP), H.323, and the like.

The dedicated communications network 10 is coupled to one or moreprivate networks 16 a, 16 b (collectively referenced as 16) over networkconnection(s) 28, 38, and to one or more remote computing environments24 over network connection(s) 26. The private networks 16 may be managedby one or more telecommunications companies that provide quality ofservice guarantees for VoIP calls traversing the private networksaccording to provider policies and limits of service ordered by itscustomers. According to one embodiment, the private networks 16implement MPLS (Multi-Protocol Label Switching) for transmitting VoIPcommunication. Although MPLS is used as an example, a person of skill inthe art should recognize that any other mechanism in addition or in lieuof MPLS may be used for ensuring quality of service guarantees, bitrates, and bandwidth for calls traversing the private networks. Due tothe quality of service guarantees provided by the private networks 16,consistent call quality and security can generally be expected for thosecalls while traversing the private networks.

According to one embodiment, agents for a particular tenant access theprivate network 16 a over link 34 (hereinafter referred to as tenantMPLS link). The amount of bandwidth provided by link 34 for theparticular tenant depends on the type of connection ordered by thetenant from the telecommunications company managing the private network.End users 14 communicating over traditional public switched telephonynetwork (PSTN) access the private network 16 b for VoIP communicationvia a SIP trunk equipment 18. Although a SIP trunk equipment 18 is usedaccording to one embodiment for accessing the private network 16 b, aperson of skill in the art should recognize that any other device forallowing legacy phone systems access to the private network 16 b forVoIP communication may be used in addition or in lieu of the SIP trunk.

According to one embodiment, the SIP trunk equipment 18 a establishes alink 38 (hereinafter referred to as the SIP trunk link) between the SIPtrunk equipment 18 and the dedicated communications network 10 over theprivate network 16 b. The SIP trunk link 38 includes dedicated accesscircuits on the private network 16 b for accessing the dedicatedcommunications network 10. The SIP trunk link 38 is shared by thecustomers 14 to access the dedicated communications network 10.

According to one embodiment, the remote computing environment 24 is acloud computing environment that utilizes public and/or private cloudservers. According to one embodiment, instead of hosting all of thecontact center applications at servers located in the dedicatedcommunications network, the applications are hosted by a server system30 in the remote computing environment 24. Such contact centerapplications include but are not limited to applications that provideVoIP signaling, voice treatments (e.g. interactive voice responseapplications), multi-call management (e.g. conference calls), and thelike.

When a contact center receives an inbound call or engages in an outboundcall campaign, all or a portion of the call is serviced by one or morecontact center applications in the remote computing environment 24 overa media path 17. According to one embodiment, the contact centerapplications for a particular tenant may be transitioned/moved from oneremote computing environment 24 to another, in the same or differentregion, in a seamless manner. The assignment of the applications totenants may be dynamically controlled based on demand and availabilityof the applications. The contact center applications may also be sharedamongst different contact centers.

Media traffic may be exchanged between customers/agents and the serversystem 30 over the media path 17 in response to invoking the contactcenter applications in the remote computing environments 24. A majorityof the voice communication, however, is conducted over a media path 20that connects the agents and customers over the private networks, butdoes not traverse the remote computing environment. Thus, thecommunication that traverses the media path 20 is generally not affectedby any potential traffic or unhealthy status of the network connection26 between the dedicated communications network 10 and the remotecomputing environment 24. In this regard, in the embodiment where cloudservers are utilized, the system in FIG. 1 may be described as a hybridcloud system where infrastructure and applications for handling calls toand from a contact center are distributed between the dedicatedcommunications network 10 and cloud servers in the remote computingenvironment 24.

According to one embodiment, agents 12 may also access contact centerapplications in the remote computing environment 24 over a public widearea network 32 such as, for example, the Internet. For example, theagents may conduct less time sensitive actions such as receiving andresponding to email, engaging in chat sessions, retrieving customerand/or statistics data, engaging in third party call controls, and thelike, over the public wide area network 32.

According to one embodiment, the server system 30 in the remotecomputing environment 24 is configured to monitor different segments ofthe network for managing media traffic. The monitoring is configured toobtain information on the status of the different segments including,without limitation, bandwidth consumption, jitter, latency, and thelike. For example, the server system may monitor the status of thetenant MPLS link 34 and/or the SIP trunk link 38. The server system 30may also monitor the status of the shared network connection (tenantnetwork connection) 28 between the private networks 16 and the dedicatedcommunications network 10. The server system 30 may further monitor thestatus of the shared network connection 26 between the dedicatedcommunications network 10 and the remote computing environments 24.Based on such monitoring, the server system 30 may be configured totrigger one or more appropriate system reactions.

For example, upon detecting a shortage of a shared resource, such as,for example, shortage of the shared bandwidth of the network connection26 between the dedicated communications network 10 and a current remotecomputing environment 24, the system may be configured to offload futuremedia traffic to a peer remote computing environment so that the serversystem in that peer remote computing environment can service the futuremedia traffic instead of the server system in the current remotecomputing environment.

The re-directing of the media traffic may be performed by a trafficmanagement module running one or more traffic management algorithms thattake into account the types of media services to be provided such as,for example, voice treatments to be provided for agents engaged inoutbound campaigns, voice treatments to be provided for inbound calls,conference call management, and the like. The traffic managementalgorithms may also take into account the class of service ordered bythe various tenants so that offloading is not only based on the type ofmedia service to be provided, but the class of service subscribed bytenants for whom the media service is to be provided. For example, thetraffic management algorithm may select voice treatments for outboundcampaigns as the type of media service to be offloaded first to the peerremote computing environment. For such voice treatments, the trafficmanagement algorithm may determine that bronze level tenants areaffected first by the offloading as having the lowest class of service,followed by silver and, eventually, gold level tenants.

With respect to the monitoring of the status of the tenant MPLS link 34,such monitoring may aid a tenant to graciously resolve an “over-booking”issue. In this regard, a tenant may subscribe to a traffic burstmanagement service provided by the system. When an unexpected burst ofcalls to be handled by the agents of the subscribing contact center isdetected by the server system, the server system may invoke theappropriate traffic management algorithm for applying servicedegradation measures for the tenant to ensure that established andprojected conversations are provided with proper quality of service.Such service degradation measures may be set by default by the systemand/or customized by the tenant. The service degradation measures mayinclude, for example, canceling an outbound campaign, activating a“sorry” greeting for new inbound calls by customers, and the like.

FIG. 2 is a schematic block diagram of two peer regions 90 a, 90 b eachsupporting a system 1 a, 1 b for dynamic management and redistributionof contact center media traffic according to one embodiment of theinvention. Systems 1 a, 1 b are similar to the system 1 described withrespect to FIG. 1. The dedicated communications network 10 a of thelocal region 90 a, is coupled to the dedication communications network10 b of the peer region 90 b over a network link 42. According to oneembodiment, the network link 42 connects the dedicated communicationsnetwork 10 a of the local region 90 a, to the dedicated communicationsnetwork 10 b of the peer region 90 b. According to one embodiment, thepeer regions 90 a, 90 b are geographically dispersed.

According to one embodiment, the server system 30 a in the local region90 a monitors the bandwidth and/or other health status of the connection26 a between the dedicated communications network 10 a and the remotecomputing environment 24 a in its region. In the event the connectionstatus satisfies a preset threshold or otherwise indicates that a systemreaction is required, the server system 30 a selects the peer region 90b to gradually offload future voice communications. The selection of thepeer region 90 b is based on a peer selection algorithm which, amongother things, takes into account the bandwidth and/or status of thenetwork link 42 connecting the dedicated communications network of thelocal region 90 a to the dedicated communications network of the peerregion, allowed bandwidth for media offload in the peer region, roundtrip response time of the server system 30 b in the peer region, statusof redundant connections in the peer region, and the like. The voicecommunication that is selected to be offloaded depends on the type ofvoice communication, the tenants that are involved, the class of serviceordered by the tenants, and other parameters set forth by the trafficmanagement algorithm.

Once the peer region 90 b is selected, the server system 30 a in thelocal region 90 a signals the server system 30 b in the peer region toservice the calls selected by the traffic management algorithm. Inresponse to such signaling, a media path 17 b is established between anagent/end user in the local region 90 a, and the server system 30 b inthe peer region 90 b. The media path 17 b is used to service theoffloaded call via one or more contact center applications in the peerserver system 30 b.

FIG. 3A is a schematic block diagram depicting details of a dedicatedcommunications network 10 a according to one embodiment of theinvention. The dedicated communications network 10 a includes an edgedevice 22 a coupled to one or more first firewalls 50 a and one or moresecond firewalls 52 a. The dedicated communications network 10 aaccesses external networks such as, for example, the private networks16, over an edge router 48. The dedicated communications network 10 amay also include other network devices 46 a as will be apparent to aperson of skill in the art.

According to one embodiment, the edge device 22 a is a session bordercontroller which controls signaling and media streams involved insetting up, conducting, and tearing down voice conversations or othermedia communications. Any session border controller conventional in theart may be used to implement the edge device 22 a. In this regard, thesession border controller includes a processor executing softwareinstructions and interacting with other system components to controlvoice or other media communications. The session border controller alsoincludes an addressable memory for storing software instructions to beexecuted by the processor. The memory is implemented using a standardmemory device, such as a random access memory (RAM).

According to one embodiment, the edge device 22 a receives callsignaling messages for setting up or tearing down a call. Such signalingmessages may include SIP signaling data such as, for example, INVITE,TRYING, REFER, ACK, 100, 200, BYE, etc., and/or SDP payload data suchas, for example, IP addresses and port numbers used for the call. Theedge device 22 a also receives media streams which carry the call'saudio, video, or other data transmitted using RTP or other similar mediacommunication protocol conventional in the art, along with informationon call statistics, quality, and the like. Together, these streams makeup a session which is controlled by the edge device. Once a connectionis established between a customer and an agent, the edge device 22 aestablishes the media path 20 for carrying a voice conversation betweenthe customer and the agent.

The firewalls 50 a and 52 a coupled to the edge device 22 a allow thehandling of security of voice conversations between, respectively, theprivate networks 16 and the dedicated communications network 10, and theremote computing environments 24 and the dedicated communicationsnetwork. Any firewall conventional in the art may be used to implementthe firewalls 50 a, 52 a. According to one embodiment of the invention,data traffic does not traverse the edge device 22 a and instead,traverses the two firewalls 50 a, 52 a over link 47 a. Additionaldevices 44 a may be coupled in between the two firewalls 50 a, 52 a forrendering additional functionality needed for transmitting the datatraffic. Such functionality may include, for example, DNS (Domain NameSystem) functionality for translating a domain name into an IP address.

FIG. 3B is a schematic block diagram depicting details of a dedicatedcommunications network 10 b according to another embodiment of theinvention. The dedicated communications network according to thisembodiment includes an edge device 22 b, firewalls 50 b, 52 b, edgerouter 48 b, link 47 b, and network devices 46 b which are similar tothe edge device 22 a, firewalls 50 a, 52 a, edge router 48 a, link 47 a,and network devices 46 a of FIG. 3A. However, according to thisembodiment, the edge device 22 b is already configured with firewallfeatures so that connection to additional hardware firewalls 50 b, 52 bare not required for providing security for voice conversations. Thefirewalls 50 b, 52 b, however, are still used for providing security fordata traffic traversing the dedicated communications network 10 b.

FIG. 4 is a more detailed schematic block diagram of the server system30 in the remote computing environment 24 according to one embodiment ofthe invention. The server system 30 includes without limitation, a SIPserver 60, universal resource server (URS) 62, media server 64, andstatistics server 66. According to one embodiment, the servers 60-66 ofthe server system are implemented as software components deployed on asingle instance of a virtual server. The single instance of the virtualserver may be implemented via standard hardware components such as, forexample, one or more processors, disks, memories, and the like. Althoughthe servers 60-66 are assumed to be separate functional units, a personof skill in the art will recognize that the functionality of two or moreservers may be combined or integrated into a single server, or furthersubdivided into additional server components without departing from thespirit of the invention. In addition, although the servers 60-66 of theserver system are depicted as being connected over a data communicationsbus 68, a person of skill in the art should recognize that there wouldbe no communication among the servers if they were implemented to residein a single physical device (e.g. a single processor). In addition, aperson of skill in the art should recognize that the server system 30 isscalable and may include a considerable number of servers 60-66 sharinga set of storage devices 70. Thus, the particular implementation of theserver system 30 depicted in FIG. 4 is solely for illustration purposes,and do not preclude other arrangements or components that will beevident to a person of skill in the art.

According to one embodiment, the SIP server 60 is configured to receivecall signaling messages (e.g. SIP INVITE messages) from the edge device22, media server 64, URS 62, and the like, for controlling the settingup or termination of a call.

The statistics server 66 provides real time states and statistics forone or more call centers, including agent availability, call handlingtime, estimated waiting time in queue, and other statistical informationassociated with call center functions. In this regard, the statisticsserver has access to one or more mass storage devices 70 storing callcenter data and software programs useful for one or more contactcenters. The one or more mass storage devices 70 may be implemented ashard disk drives or other suitable mass storage devices conventional inthe art.

The URS 62 may be configured to access the statistics server 66 toidentify agents based on skills, availability, and the like, for inboundand/or outbound calls, and forward call signaling messages to the SIPserver 60 to transmit call requests to the identified agents.

The media server 64 is configured to identify parameters (e.g. availablemedia ports on the media server) for establishing voice conversationsbetween agents and customers, and provide those parameters to the SIPserver for delivering to the edge device, customers, and agents. Themedia server 64 is also configured to deliver media to customers and/oragents via the edge device 22. For example, the media server 64 may beinvoked to provide initial greeting messages to a calling customer, andfor obtaining basic customer information (e.g. identificationinformation, reason for the call, etc.). Also, if the customer or agentis placed on hold, the media server 64 may be invoked to play music forthe holding customer or agent. In another example, if a conversationbetween a customer and agent is to be recorded, the call may traversethe media server so that the customer and agent engage in a three wayconversation with the media server, and the media server records theconversation and stores it in the mass storage device 70.

According to one embodiment of the invention, the SIP server 60 includesa traffic management module 72 for providing traffic burst managementservices for one or more tenants of the system. In this regard, themodule is configured to monitor various network segments, determine astatus for the various segments, and provide management and redirectionservices based on the determined status. Although in the illustratedembodiment the traffic management module 72 is depicted as being hostedby the SIP server 60, a person of skill in the art should recognize thatthe module may also be hosted by one or more other servers of the serversystem 30. Also, the functionality of the traffic management module 72may be subdivided into sub-modules, each sub-module being hosted in asingle server or distributed among various servers of the server system30.

According to one embodiment, the traffic management module 72 isconfigured to monitor the following network segments and theirconnectivity:

-   -   Tenant network connectivity:        -   Bandwidth of the tenant MPLS link 34 a.    -   Network connectivity of the local region 90 a (FIG. 2) and        network connectivity of a peer region 90 b:        -   Provisioned bandwidth of the network connection 26 a between            the remote computing environment 24 a and the dedicated            communications network 10 a in the local region 90 a;        -   Provisioned bandwidth of the network link 42 between            dedicated communications network 10 a of the local region            and the dedication communications network 10 b of the peer            region;        -   Provisioned bandwidth of the network connection 26 b between            the remote computing environment 24 b and the dedicated            communications network 10 b in the peer region;        -   Provisioned bandwidth of the SIP trunk link 38 a between the            SIP trunk equipment 18 a and the dedicated communications            network 10 a in the local region;        -   Provisioned bandwidth of the network connection 28 a between            the dedicated communications network 10 a and tenants in the            local region.

According one embodiment, the traffic management module 72 identifiesthe connections that get impacted when a call reaches a call progressstate, and calculates the portion of the bandwidth that is consumed forthe impacted connections. According to one embodiment, the availablebandwidth of a particular connection is equal to the provisionedbandwidth (minus a portion pre-allocated for SIP signaling). Everyestablished voice conversation decreases the available bandwidth in oneor more segments of the network. Finished voice conversations releasethe consumed bandwidth and increase the available bandwidth.

Specifically, every voice conversation involving an agent 12 decreasesthe available bandwidth of the tenant MPLS link 34 a, and the availablebandwidth on the network connection 28 a between the dedicatedcommunications network 10 a and the tenants in the local region, whichis shared among the various tenants.

Every voice conversation involving the server system 30 a in the localregion decreases the available bandwidth of the network connection 26 abetween the remote computing environment 24 a and the dedicatedcommunications network 10 a in the local region.

Every voice conversation involving an end user 14 in the local regiondecreases the available bandwidth of the SIP trunk link 38 a between theSIP trunk equipment 18 a and the dedicated communications network 10 ain the local region.

Every voice conversation offloaded to the server system 30 b in the peerregion 90 b decreases the available bandwidth of the network link 42between the local data communications network 10 a and the datacommunications network 10 b of the peer region, and the availablebandwidth of the connection between remote computing environment 24 band the dedicated communications network 10 b in the peer region.

According to one embodiment, the server system 30 maintains a count ofestablished voice conversations and associates their impact on thenetwork. In this manner, the server system monitors the status ofdifferent connections and/or operational status of the entire networktopology, detecting bottlenecks within the network and other ailments inthe monitored segments. When a bandwidth threshold is reached for one ormore monitored network connections, the server system 30 appliesappropriate measures selected by the traffic management algorithm.

FIG. 5 is a schematic diagram depicting the flow of signals between thevarious components of the system for processing an inbound call from anend user 14 to a contact center according to one embodiment of theinvention. In step 80, the end user 14 transmits a packet with a requestfor a call conversation (e.g. a SIP INVITE) to the edge device 22, andthe requested conversation causes utilization of the SIP trunk link 38.The edge device processes the packet according to well known mechanisms,and in step 82, sends a converted packet to the SIP server 60 over thenetwork connection 26. In step 84, the SIP server 60 forwards the packetto the media server 64.

If the media server 64 is available to identify an available port forvoice conversation, call parameters for establishing the voiceconversation via the identified port are sent back to the SIP server 60in step 86.

The SIP server 60 in turn passes the parameters to the edge device 22over the network connection 26 in step 88, and the edge device passesthe parameters to the end user 14 in step 89. An RTP media path 17 (viasteps 90 and 92) is then established between the end user 14 and themedia server 64 in the remote computing environment 24, via the edgedevice 22. The media server 64 transmits over the media path an initialgreeting and other voice treatments for prompting the end user 14 toprovide identification information and/or reasons for the call. Over themedia path 17, the end user provides such information to the edge device22, which then forwards the information to the media server 64.

Although not depicted in FIG. 5, the SIP server 60 communicates with theURS 62 which in turn communicates with the statistics server 66 fordetermining an agent to which the call is to be forwarded. Thedetermination of such agent may be based on available agents, theirskill, and the like. Once such an agent is identified, the SIP server 60transmits a message to the edge device 22 in step 94, which then signalsthe selected agent 12 in step 96.

In response to the signaling, in step 98, the agent forwards hisparameters for the voice conversation to the edge device 22. The edgedevice forwards the parameters to the SIP server in step 100, using SIPsignaling understood by the SIP server. The SIP server re-invites theend user 14 for the conversation with the agent by transmitting a SIPpacket to the end user in steps 102 and 104, via the edge device 22.This conversation utilizes bandwidth on tenant links 28 and 34. Once theend user accepts the invitation, the RTP media path 20 which iscontrolled by the edge device 22 is established (via steps 106 and 108)between the agent 12 and the end user 14. This media path does nottraverse the network connection 26 to the remote computing environment24.

FIG. 6 is a flow diagram of an offload process implemented by thetraffic management module 72 of the server system 30 according to oneembodiment of the invention. According to the process, the trafficmanagement module monitors, in step 110, status of various networksegments including status of the network connection 26 a between thededicated communications network 10 a and the remote computingenvironment 24 a. Such monitoring may be done in real time and mayinclude, for example, determination as to the number of active calls inprogress which are currently being handled by a media server 64 in thelocal region, and a determination of the type of media service beingrendered for each call. This information may be used to calculate atotal amount of bandwidth consumed for the network connection 26 a, andto further estimate growth of call flows involving the local mediaserver. The general “health” of the network connection 26 a may also bemonitored, in addition or in lieu of the bandwidth saturation. Forexample, the system may perform regular SNMP-based monitoring of thenetwork devices providing redundant network connections between thecommunications network 10 a and the server system 30 a.

In step 112, a determination is made as to whether a threshold or othercriteria for offloading has been satisfied. For example, the trafficmanagement module may determine whether the bandwidth saturation of thenetwork connection 26 a has reached a certain level. If the answer isYES, the traffic management module, in step 114, determines whetherthere is a peer region available for selection from one or more remoteregions to which gradually offload media. According to one embodiment,the selection of the peer region is based on a peer selection algorithmwhich takes into account one or more parameters, such as, for example,the geographic location of the remote regions, bandwidth saturation ofthe network link 42 connecting the local region to the remote regions,allowed bandwidth for media off-load in the remote regions, roundtripresponse time of the remote media server, status of the redundantconnections at the remote regions, and the like.

If a peer region is available for selection, the traffic managementmodule selects an appropriate peer in step 116.

In step 118, the traffic management module 72 selects one or moretenant(s) whose media is to be offloaded. The selection of theparticular tenant may be based on the class of service ordered by thetenant. For example, the traffic management module may be configured toselect tenants associated with the lowest (bronze) class of service andinitially offload media connection requests for these types of tenantsto the selected peer region. The level of service provided to a tenantout of the peer region is configured to match the level of service thetenant had prior to the offloading.

In step 120 the traffic management module is configured to select one ormore different types of media to be offloaded first for the selectedtenant. According to one embodiment, the order in which different typesof media are offloaded may be set by default. For example, mediaprovided to agents during an outbound campaign may be selected first bydefault for offloading since the quality or latency of such media to theagents is not critical. The tenants may also indicate their preferenceas to the order in which different types of media are to be offloaded,in each tenant's profile record stored in the mass storage device 70.

In step 122, the traffic management module sets an identifier of themedia server of the selected peer region as the default media server forservicing the selected media type of the selected tenants. The mediaidentifier may be stored, for example, in the profile record of theselected tenants, in association with the selected media type.Thereafter, requests to the local SIP server 60 requiring servicing by acontact center application in a media server are redirected to the peermedia server over the network link 42 in a seamless manner.

Referring again to step 114, if a peer region is not available forselection, the traffic management module 72 activates an emergencyprocess in step 124. The emergency process may entail, for example,canceling all outbound campaigns, delivering new call to an availableagent without initial treatment, instructing the local SIP Server 60 torefuse all inbound calls, and the like.

Referring again to steps 110 and 112, if the monitoring of the status ofthe network connection 26 a indicates that the threshold or othercriteria for offloading has not been satisfied (e.g. there is sufficientbandwidth on the network connection 26 a), the traffic management moduledetermines in step 126 whether any tenants have calls redirected to apeer region. If the answer is YES, the traffic management moduleselects, in step 128, one or more tenants to revert back to the localregion. The selection of such tenants may depend, for example, on theclass of service subscribed, the different geographic locations of thepeer regions (if more than one) to which the tenants have beenredirected, and the like.

In step 130, the traffic management module selects one or moreredirected media types to revert back to the local region.

In step 132, the traffic management module sets an identifier of themedia server of the local region as the default media server forservicing the selected media type(s) of the selected tenant(s). Themedia identifier may be stored, for example, in the profile record ofthe selected tenant(s).

In addition or in lieu of monitoring and managing traffic traversing thenetwork connection 26, the traffic management module also monitorsbandwidth of a tenant for managing traffic bursts on a per tenant basis.In this regard, the mass storage device maintains information about eachtenant in a tenant profile record stored in the mass storage device 70.

FIG. 7 is a semi-schematic, conceptual layout diagram of a portion of atenant's profile record 400 providing information on call resourcesavailable to the tenant according to one embodiment of the invention.The information in the record 402 may be provided by the tenant whensubscribing to one or more call center services, or automaticallydeduced from monitoring activities of each tenant. In the illustratedembodiment, the record 400 stores a typical number of simultaneous voiceconversations handled by the tenant 402, a maximum expected number ofvoice conversations 404, a maximum number of agents for which thetenant's call center is configured 406, and a number of actual agents408 that the tenant is providing along with information on their skilllevel (regular 410 or skilled 412). The record 400 further stores anumber of maximum number of supervisors for which the tenant's callcenter is configured 414, and a number of actual supervisors that thetenant will provide 416.

FIG. 8 is a semi-schematic, conceptual layout diagram of another portionof a tenant's profile record 140 for storing information on thebandwidth characteristics of the tenant MPLS link 34 subscribed to bythe tenant for connecting to the dedicated communications network 10according to one embodiment of the invention. For example, the record140 may indicate a regular bit rate at the tenant premises 142,available normal traffic burst bandwidth 144, and available extendedburst bandwidth 146. The record 140 may also provide information on thephysical media bandwidth limit 148 of the MPLS link 34. According to oneembodiment, the burst levels are managed by the provider of the privatenetwork 16. Exceeding the extended burst level 146 generally causesdropping of packets controlled by the provider's bandwidth managementpolicies. Exceeding the physical media bandwidth 148 also leads to thedropping of packets by the hardware involved.

FIG. 9 is a semi-schematic, conceptual layout diagram of a bandwidthconsumption table 150 storing information on the bandwidth of the tenantMPLS link 34 that is estimated to be consumed for a particular tenantaccording to one embodiment of the invention. The bandwidth consumptionis estimated based on the known codec used by the tenant. In theillustrated example, each row of the table provides information, at aparticular point in time, as to a total number of end-customers thatwere served 152 by engaging in a voice conversation, a total number ofvoice conversations 154 that were simultaneously established at thattime, and estimated bandwidth consumption 156 for the simultaneouslyestablished voice conversations. The estimated bandwidth consumption forthe simultaneously established voice conversations is further brokendown to identify an estimated bandwidth consumed for voice traffic only158, and an estimated total bandwidth consumption 160 includingbandwidth consumed for SIP signaling, and the like. For the establishedvoice conversations, the table also breaks down the conversations basedon the conversation type (e.g. direct conversations 160, multi-partyconversations 162, consult calls 164, supervised calls 166, outboundcampaigns 168, and the like). According to one embodiment, theconversation type is not considered in the bandwidth consumptioncalculation and thus, may be omitted from the table; each conversationconsumes equal amount of bandwidth regardless the conversation type. Thetable 150 further tracks a number of agents 170 engaged in each type ofconversation. According to one embodiment, the traffic management module72 updates the table in real time as voice conversations are initiatedand terminated. Alternatively, the traffic management module 72 may beconfigured to periodically conduct a survey to determine the bandwidthconsumption of the tenant MPLS link 34 at the time of the survey.

The bandwidth consumption depends on the manner in which the calls arehandled. In some cases, there might be sufficient bandwidth for ten endcustomers to be served. In other cases, there may not be enoughbandwidth for even eight customers. For example, for a tenant with aprofile depicted via FIGS. 7 and 8, entry 172 illustrates a situationwhere the tenant served even more end customers than planned (i.e. hadvoice conversations with 12 customers when the maximum expected numberof voice conversations 124 (FIG. 7) was ten). However, there was stillenough bandwidth for the conversations since the 12 conversations weredirect conversations via media path 20 (FIG. 1) consuming 1.28 Mbps,which is below the 1.5 Mbps physical media limit available to thetenant. All top rows 174 of the table indicate that the bandwidthconsumed by the conversations was below the 1.5 Mbps physical medialimit available to the tenant. The middle rows 176 of the table indicatethat the consumed bandwidth was at the physical media limit. The bottomrows 178 of the table indicate that even though staffing (e.g. number ofagents and supervisors) was within the ordered limits as depicted inFIG. 7 (15 agents and two supervisors), and the number of calls from endcustomers was also within the ordered limits (ten customers), the amountof bandwidth consumed due to the type of calls being serviced was high,causing it to exceed the 1.5 Mbps physical media limit available for thevoice conversations. In this case, quality of established voiceconversations is lost, and the tenant often experiences dropping ofpackets and the like. A bandwidth upgrade for the tenant MPLS link 34 isthus often required.

According to one embodiment of the invention, a tenant may subscribe toa traffic burst management service for controlling the servicedegradation to its customers when there is an over consumption ofbandwidth of the tenant MPLS link 34, as is reflected via the bottomrows of the bandwidth consumption table 150 of FIG. 9. Whether thetenant has subscribed to such a service may be determined by examiningthe tenant's profile record. A subscribing tenant may be prompted,electronically or otherwise, to provide the bandwidth subscriptioninformation for storing in the record 140 of FIG. 8.

FIG. 10 is a flow diagram of a process executed by the trafficmanagement module 72 for managing traffic bursts on a per tenant basisaccording to one embodiment of the invention. In step 200, the trafficmanagement module identifies a tenant subscribed to the traffic burstmanagement service. This may be done, for example, by examining anappropriate field of each tenant's profile record for an indication thatthe tenant has subscribed to such a service.

In step 202, the traffic management module 72 calculates the estimatedbandwidth consumption of the tenant MPLS link 34. In this regard, thetraffic management module determines a number of simultaneouslyestablished voice conversations traversing the tenant MPLS link 34,regardless of the type of conversations being conducted. A totalestimated bandwidth consumption is then calculated based on the numberof voice conversations.

In step 204, the tenant's bandwidth consumption table 150 (FIG. 9) isupdated with the calculated information.

In step 206, the traffic management module 72 determines whether athreshold bandwidth consumption amount has been satisfied. The thresholdmay be provided by the tenant or calculated automatically by the trafficmanagement module based on the bandwidth characteristics of the tenantMPLS link 34 stored in the record 140 (FIG. 8). For example, the trafficmanagement module 72 may automatically calculate the threshold as apreset percentage (e.g. 75%) of the physical media bandwidth limitpurchased by the tenant.

If the threshold bandwidth consumption level has been satisfied, adetermination is made in step 208 as to whether the tenant has provideda customized service degradation measure/plan. If the answer is YES, thetraffic management module invokes the customized degradation measure.Otherwise, the traffic management module selects a default degradationmeasure.

Regardless of whether the degradation measure is customized or adefault, the traffic management module is configured to apply themeasure to future voice conversations traversing the tenant MPLS link34. For example, the degradation measure may start with canceling anoutbound campaign on behalf of the tenant until additional bandwidth ofthe tenant MPLS link becomes available. In this regard, the trafficmanagement module 72 identifies an outbound campaign for the tenantbased on the tenant identification information, and either cancels thecampaign or reschedules it for another time and/or date. If there are nooutbound campaigns to cancel/reschedule, the degradation measure mayactivate “sorry” greetings toward new inbound calls of end customers 14.Thus, instead of abruptly refusing new calls, the “sorry” greetings maymore graciously turn down such new calls, redirect the call to a voicemail system, and may even request a call back number that an agent maycall at a later time.

According to one embodiment, the traffic management module 72 is alsoconfigured to gracefully manage unexpected call rate bursts in theentire system. FIG. 11 is a flow diagram of a process for managingunexpected call rate bursts for the entire system according to oneembodiment of the invention. The process starts, and in step 300, thetraffic management module monitors the status of the SIP trunk link 38.Such monitoring may include, for example, determination as to the numberof simultaneously established voice conversations with an end-user 14for the entire system, and the type of calls that are being conducted.Based on this information, the traffic management module may beconfigured to calculate a total amount of bandwidth consumed for the SIPtrunk link 38.

In step 302, the traffic management module makes a determination as towhether a threshold bandwidth consumption amount has been satisfied. Thethreshold may be calculated automatically by the traffic managementmodule based on the bandwidth characteristics of the SIP trunk link 38.For example, the traffic management module 72 may automaticallycalculate the threshold as a preset percentage (e.g. 75%) of thephysical media bandwidth limit of the SIP trunk link.

If the threshold bandwidth consumption level has been satisfied, atenant is selected in step 304 for invoking a service degradationmeasure for the selected tenant. In this regard, the traffic managementmodule identifies for each tenant, the level of service/class of serviceordered by the tenant. This information may be stored, for example, ineach tenant's profile record. The record may indicate that the tenanthas ordered a bronze, silver, or gold level service. The trafficmanagement module may be configured to select tenants with a lower levelof service (e.g. bronze level tenants) prior to selecting tenants of ahigher level of service (e.g. silver or gold level tenants).

In step 306, the traffic management module is configured to invoke aservice degradation measure for the selected tenant(s). The servicedegradation measure may be similar to the service degradation measurediscussed above with respect to FIG. 10.

According to one embodiment, although the monitoring in FIGS. 10 and 11is described as monitoring the bandwidth consumption of respectively thetenant MPLS link 34 and the SIP trunk link 38, a person of skill in theart should recognize that the general “health” of the tenant and SIPtrunk links may also be monitored in addition or in lieu of thebandwidth saturation, similar to the monitoring of the “health” of thenetwork connection 26 a as is described above with respect to FIG. 6.

The processes described with respect to FIGS. 6, 10, and 11 may bedescribed in terms of a software routine executed by a processor in theserver system 30 based on instructions stored in the server's memory.The instructions may also be stored in other non-transient computerreadable media such as, for example, a CD-ROM, flash drive, or the like.A person of skill in the art should also recognize that the routine maybe executed via hardware, firmware (e.g. via an ASIC), or in anycombination of software, firmware, and/or hardware. Furthermore, thesequence of steps of the various processes is not fixed, but can bealtered into any desired sequence as recognized by a person of skill inthe art.

It is the applicants intention to cover by claims all such uses of theinvention and those changes and modifications which could be made to theembodiments of the invention herein chosen for the purpose of disclosurewithout departing from the spirit and scope of the invention. Thus, thepresent embodiments of the invention should be considered in allrespects as illustrative and not restrictive, the scope of the inventionto be indicated by the appended claims and their equivalents rather thanthe foregoing description.

1. A system for managing media traffic for a plurality of customercontact centers, the system comprising: first and second server systemsin respectively first and second computing environments, the first andsecond server systems hosting contact center applications for processingcommunication to and from the one or more contact centers; and an edgedevice deployed in a first communications network for facilitating afirst communication involving a first end device and for signaling thefirst server system to service the first communication, wherein mediatraffic is transmitted between the first end device and the first serversystem during the first communication in response to the servicing, theservicing invoking a first contact center application hosted by thefirst server system, the media traffic traversing a first network linkcoupling the first communications network and the first computingenvironment, wherein, the first server system is configured to monitorstatus of the first network link and in response to the monitoring,signal the second server system in the second computing environment toservice a second communication involving a second end device, whereinthe servicing of the second communication invokes a second contactcenter application hosted by the second server system.
 2. The system ofclaim 1, wherein the first and second communications are voicecommunications.
 3. The system of claim 1, wherein the media traffic isvoice traffic.
 4. The system of claim 1, wherein the first and secondcomputing environments are cloud computing environments.
 5. The systemof claim 1, wherein the monitoring of the status of the first networklink includes monitoring the bandwidth of the first network link.
 6. Thesystem of claim 1, wherein a second communications network is coupled tothe first communications network over a second network link, the secondcommunications network being further coupled to the second computingenvironment, wherein the first server system is further configuredmonitor status of the second network link and select the secondcomputing environment for servicing the second communication based onthe monitored status of the second network link.
 7. The system of claim6, wherein the second communication is configured to generate trafficthat traverses the second network link.
 8. The system of claim 1,wherein a second communications network is coupled to the secondcomputing environment over a second network link, wherein the firstserver system is further configured monitor status of the second networklink and select the second computing environment for servicing thesecond communication based on the monitored status of the second networklink.
 9. The system of claim 1, wherein the first server system isconfigured to select a media type, the first server system being furtherconfigured to signal the second server system in the second computingenvironment if the second communication is of the selected media type.10. The system of claim 9, wherein the selected media type is voicetreatment in an outbound campaign by one or more of the plurality ofcustomer contact centers.
 11. The system of claim 9, wherein theselected media type is voice treatment for an inbound call directed toone or more of the plurality of customer contact centers.
 12. The systemof claim 9, wherein the selected media type is a multi-party call. 13.The system of claim 1, wherein the first server system is configured toselect a contact center service level from a plurality of availableservice levels, and further configured to signal the second serversystem in the second computing environment if the second communicationis associated with a customer contact center assigned to the selectedcontact center service level.
 14. The system of claim 1, wherein thefirst end device accesses a private network over a second link, theprivate network being coupled to the first communications network,wherein the first server system is configured to identify one of theplurality of customer contact centers associated with the firstcommunication, determine availability of the second link for theidentified customer contact center, and in response to the determinedavailability, trigger an action for preserving a particular quality ofservice for the voice communication.
 15. The system of claim 14, whereindetermining availability of the second link includes determiningestimated available bandwidth of the second link.
 16. The system ofclaim 14, wherein the second link is accessed by an agent of theidentified customer contact center via the first end device.
 17. Thesystem of claim 14, wherein the triggered action is canceling anoutbound campaign for the identified customer contact center.
 18. Thesystem of claim 14, wherein the triggered action is activating agreeting for delivery to the first end user, the greeting for indicatinginability for servicing the voice communication.
 19. The system of claim1, wherein the first end device accesses the first communicationsnetwork over a second link coupling the first communications network toa private network, wherein the first server system is configured todetermine availability of the second link based on calls traversing thesecond link, wherein, in response to the determined availability of thesecond link, the first server system is configured to trigger an actionwith respect to calls associated with contact centers subscribed to afirst service level for preserving a particular quality of service forcalls associated with contact centers subscribed to a second servicelevel different from the first service level.
 20. The system of claim19, wherein determining availability of the second link includesdetermining estimated available bandwidth of the second link.
 21. Thesystem of claim 19, wherein the second link is shared by customers ofthe contact centers subscribed to the first and second service levels.22. The system of claim 19, wherein the triggered action is canceling anoutbound campaign for one or more of the contact centers subscribed tothe first service level.
 23. The system of claim 18, wherein thetriggered action is activating a greeting for delivery to one or morecustomers of one or more of the contact centers subscribed to the firstservice level, the greeting for indicating inability for servicing acall by the one or more customers.
 24. A method for managing mediatraffic for a plurality of customer contact centers accessing a computernetwork, the method comprising: receiving by an edge device a firstcommunication involving a first end device, the edge device beingcoupled to a first communications network; signaling by the edge devicea first server system to service the first communication, wherein inresponse to the signaling, the first server system invokes a firstcontact center application hosted by the first server system, the firstserver system being hosted by a first computing environment;transmitting media traffic between the first end device and the firstserver system during the first communication in response to theservicing, the media traffic traversing a first network link couplingthe first communications network and the first computing environment,monitoring status of the first network link; in response to themonitoring of the first network link, signaling a second server systemin a second computing environment for servicing a second communicationinvolving a second end device, wherein the servicing of the secondcommunication invokes a second contact center application hosted by thesecond server system. 25-26. (canceled)